Repository navigation
π competitor report: publication gate accepts a fenced project table on GitHub - #17711
Conversation
β¦ublication gate Catch-up run actions/runs/43065486702 failed with 'GitHub "Who does what" section needs a Markdown table': the agent rendered the table as a fenced block on GitHub too. Read project names from either a Markdown pipe table or a fenced block of aligned columns. Signed-off-by: Andrew Anderson <andy@clubanderson.com>
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clubanderson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Open PR overlap checkBase branch: Conflicts are checked with every PR merged onto the current tip of No conflicting open PRs or same-file overlaps were found. |
|
merged by Hive trusted-author auto-merge: author @clubanderson holds role owner and GitHub permission admin on repo; CI green at 0b5308f. |
|
Thank you for your contribution! Your PR has been merged. We'd love to hear how your experience was: share feedback |
Follow-up to #17705. The catch-up run https://github.com/hivecommons/hive/actions/runs/43065486702 got through the Discord comparison but failed on
because this time the agent rendered the project table as a fenced block on GitHub as well (the prompt only says "a compact table").
table_projects()now reads project names from either a Markdown pipe table or a fenced block of aligned columns (first column, split on|or 2+ spaces). Replayed both the 11-09 and 11-11agent_output.jsonartifacts through the gate: both pass. Regression test added.Refs #14613